feat(anolisa): add native dsh adapter - #2580

Why

ANOLISA components need a framework-native way to register plugin bundles with
DeepSeek Harness without editing $DSH_HOME or maintaining component-specific
install scripts. This adds a reusable DSH driver so Tokenless and future
components can use the same adapter contract and DSH-owned lifecycle.

What changed

• Add a generic dsh framework driver that validates package.json, the
  nested dsh.bundle.patch declaration, and the Cordis patch package identity.
• Add repeatable anolisa adapter enable <component> dsh --profile <name>
  selection and reject implicit or non-DSH profile usage.
• Register and remove packages through dsh plugin --profile ..., persist one
  typed receipt for all selected profiles, verify status using exact package
  matches, and clean stale profiles during re-enable.
• Persist the validated enable-time DSH home in the receipt so status, disable,
  and re-enable cleanup remain anchored when DSH_HOME or the cwd changes.

Other components can reuse the interface by declaring a normal ANOLISA adapter:

[[adapters]]
framework = "dsh"
adapter_type = "plugin"
plugin_id = "my-plugin-id"
source = "adapters/dsh"
dest = "{datadir}/adapters/{component}/dsh/"

[adapters.bundle]
entry = "package.json"

The source directory must contain an npm-compatible package name and nested DSH
bundle metadata:

{
  "name": "@example/dsh-plugin",
  "dsh": { "bundle": { "patch": "./cordis.patch.yml" } }
}

The patch id must match plugin_id, and the plugin name must match the package
installed by DSH:

- insert:
    - id: my-plugin-id
      name: '@example/dsh-plugin'

ANOLISA then delegates registration to DSH with a link: package reference;
components do not write profile files directly.

Related issue

no-issue: introduce the shared DSH adapter contract needed by native plugins

User / Agent impact

Users can enable a component in one or more explicit DSH profiles:

anolisa adapter enable <component> dsh --profile default
anolisa adapter enable <component> dsh --profile web --profile headless

Disable and status use both the profiles and DSH home recorded by the enable
receipt.

Risk and compatibility

• Public CLI, API, configuration, or documented behavior changed
• Cross-component contract changed
• Migration or rollback guidance is needed

The change adds a profiles field to EnableOptions and a dsh receipt
payload, including the validated enable-time DSH home resource. Before
downgrading to an ANOLISA version without this driver, disable all DSH adapters
so older binaries do not encounter the new receipt variant.

Validation

• cargo fmt --all -- --check
• cargo test -p anolisa-core --locked
• cargo test -p anolisa-cli enable_parses_repeatable_profiles --locked
• cargo clippy -p anolisa-core --all-targets --locked -- -D warnings
• cargo clippy -p anolisa-cli --all-targets --locked -- -D warnings
• cargo doc --workspace --no-deps --locked
• git diff --check

Documentation and rollback

The public Rust items and CLI help document the new contract; no standalone
guide is added in this change. Roll back by disabling DSH adapters first and
then reverting this PR's feature commit.